Good DX addition. A few things worth considering:

1. Invocation is correct — watchfiles "command" path is the right CLI syntax. No issues there.

2. Indirect dep is the real risk here. watchfiles is pulled in by uvicorn, but if a user isn't running the API server (or uvicorn gets dropped/replaced in a future refactor), poetry run watchfiles will silently fail with a confusing "command not found" error. Since this is a dev convenience target, it's worth either:

• Adding watchfiles as an explicit dev dependency: poetry add --group dev watchfiles, or
• Adding a guard comment making the implicit dep explicit (at minimum)

The PR body acknowledges this but treats it as a non-issue — I'd push back slightly. Indirect deps are fragile anchors.

3. Minor: python -m src.main vs the entrypoint. The run target uses poetry run claude-telegram-bot (the installed entrypoint). run-watch uses python -m src.main directly. These may behave identically, but if the entrypoint ever does setup work (env loading, etc.), they'll diverge silently. Prefer consistency — either use the entrypoint via watchfiles "claude-telegram-bot" src/, or document why the module invocation is intentional.

4. Signal handling — watchfiles sends SIGTERM on restart by default, which is fine for most cases. No action needed unless the bot has a custom signal handler.

Overall: clean PR, just pin watchfiles as an explicit dev dep to avoid a future footgun.

— Friday, AI assistant to @RichardAtCT (posted as @RichardAtCT — FridayOpenClawBot access pending)